ADAPTIVE US INC.
Giant Book of
BABoK® v3 Glossary
Knowledge Area (KA) Wise
240% more terms defined
compared to BABoK® v3
World’s #1 IIBA® V3
Training Provider
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 2 of 114
Name:
__________________________________________
Organization:
__________________________________________
Telephone #:
__________________________________________
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 3 of 114
Copyright notice
All rights reserved.
IIBA®, BABOK®, CBAP®, CCBA®, ECBA® are registered Trademarks of
International Institute of Business Analysis, Canada.
All trademarks of copyrights mentioned herein are the possession of
their respective owners. We make no claim of ownership by the mention
of products that contain these marks.
Contents of this document should not be disclosed to any unauthorized
person. This document may not, in whole or in part, be reduced,
reproduced, stored in a retrieval system, translated, or transmitted in any
form or by any means, electronic or mechanical.
This publication may be used in assisting aspirants for ECBA
TM
, CCBA®,
and CBAP® examinations. It does not warrant that use of this
publication will ensure passing the above mentioned examination.
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 4 of 114
Why this book?
BABoK® V3 is considered as Gold standard reference on business
analysis which is published by IIBA®, Canada.
BABoK® does provide a glossary. However, it only provides a sub-set of
all terms that Business Analysts should be familiar with. Current BABoK®
V3 glossary has 250 terms explained.
This guide picks up many more terms which will be of interest to
business analysis community, brings up the total terms count to a
whopping 600 terms. This is 240% of current BABoK® V3 terms.
Hope all my business analysis friends will find this glossary helpful.
Feedbacks and suggestions on the book
We will be glad and thankful if you can share your feedbacks and
suggestions on the book. Please send your feedbacks and suggestions
to Info@AdaptiveUS.com
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 5 of 114
TABLE OF CONTENTS
COPYRIGHT NOTICE ................................................................................................................................... 3
WHY THIS BOOK? ....................................................................................................................................... 4
ABOUT ADAPTIVE US INC. ........................................................................................................................ 6
UNIQUE BENEFITS OF WORKING WITH US ............................................................................................ 7
OUR KEY CLIENTS ....................................................................................................................................... 7
ADAPTIVE WORKSHOPS CATALOGUE..................................................................................................... 8
KNOWLEDGE AREA 1 – BA PLANNING AND MONITORING ................................................................................................... 9
KNOWLEDGE AREA 2 – ELICITATION AND COLLABORATION ............................................................................................... 18
KNOWLEDGE AREA 3 – REQUIREMENTS LIFE CYCLE MANAGEMENT .................................................................................. 27
KNOWLEDGE AREA 4 – STRATEGY ANALYSIS ......................................................................................................................... 32
KNOWLEDGE AREA 5 – REQUIREMENTS ANALYSIS AND DESIGN DEFINITION ................................................................... 39
KNOWLEDGE AREA 6 – SOLUTION EVALUATION ................................................................................................................... 48
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 6 of 114
About Adaptive US Inc.
Adaptive US Inc. provides CBAP
®
,
CCBA
®
, ECBA
TM
online trainings,
question banks, study guides,
simulators, flash cards, audio books,
digital learning packs across the
globe.
Adaptive US Inc. is the only training
organization to offer success
guarantee and all-inclusive plans for
its workshops.
Key facts
World’s #1 IIBA
®
training organization
World’s largest BA publisher and
assessments provider
Premiere Partner to IIBA
®
, Canada and
IREB, Germany
300+ certified BA professionals
300+ BA workshops – 5000+ BAs trained
Our trainers are part of BABoK
®
V3 team
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 8 of 114
Adaptive workshops catalogue
Category
Course Name
Business analysis
Certified Business Analyst Professional
(CBAP®) (Endorsed by IIBA® , Canada)
Business analysis
Certification of Competency in Business
Analysis (CCBA®) (Endorsed by IIBA® ,
Canada)
Business analysis
Entry Certificate in Business Analysis
(ECBA®) (Endorsed by IIBA® , Canada)
Business analysis
Agile Analysis Certification (IIBA-AAC)
(Endorsed by IIBA® , Canada)
For the latest information, always refer to our web-site,
www.AdaptiveUS.com.
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 9 of 114
Knowledge Area 1 – BA Planning and Monitoring
Sl. #
BA Planning Terms
Definition
1
Accountable
Person who is the decision maker and who is
held accountable for successful completion of
the task
2
Achievable
Feasible. Part of SMART criteria.
3
Adaptability
Ability to adjust techniques, styles, methods
and approaches to suit the needs of the rapidly
changing environment and also deal with a
variety of stakeholders
4
Adaptive approach
An approach where the solution evolves based
on a cycle of learning and discovery, with
feedback loops which encourage making
decisions as late as possible.
5
Agile
An iterative approach to software development
6
Agile manifesto
A set of principles prescribed by Agile
practitioners
7
Approach
High level plan to achieve something
8
Body of knowledge
The aggregated knowledge and generally
accepted practices on a topic.
9
Both in and out scope
Elements on both sides of the boundary (as
seen from both sides)
10
Bottom-up estimation
Bottom-up estimation uses WBS technique to
estimate deliverables, activities, tasks
11
Burn-down
An agile approach to track sprint progress
12
Business acumen
Ability to understand business needs using
experience and knowledge obtained from
other situations
13
Business analysis
The practice of enabling change in the context
of an enterprise by defining needs and
recommending solutions that deliver value to
stakeholders.
14
Business analysis approach
The set of processes, rules, guidelines,
heuristics, and activities that are used to
perform business analysis in a specific context.
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 10 of 114
Sl. #
BA Planning Terms
Definition
15
Business analysis
communication plan
A description of the types of communication
the business analyst will perform during
business analysis, the recipients of those
communications, and the form and frequency
of those communications.
16
Business analysis effort
The scope of activities a business analyst is
engaged in during the life cycle of an initiative.
17
Business analysis
performance assessment
Comprises of a comparison of planned vs
actual performance, Root cause analysis of
deviation from the expected performance, ways
to address issues etc.
18
Business analysis
perspectives
5 perspectives of business analysis described in
BABoK - agile, business intelligence,
information technology, business architecture,
business process management
19
Business analysis plan
A description of the planned activities the
business analyst will execute in order to
perform the business analysis work involved in
a specific initiative. See also requirements
management plan.
20
Business analysis planning
and monitoring
Tasks BAs perform to organize and coordinate
efforts of BAs and stakeholders
21
Business analysis roles
Roles which typically conduct business analysis
work - business architect, system analyst,
requirements engineer, process analyst,
management consultant, product manager
22
Business analysis tools and
technology
Tools those provide specialized capabilities in
creating models and visuals for the
requirements
23
Business analyst
Any person who performs business analysis, no
matter their job title or organizational role.
24
Business Process Dimension
Measures indicating how well the enterprise is
operating and if its products meet customer
needs
25
Certification
Constraints on the solution which is necessary
to meet certain standards or industry
convention
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 11 of 114
Sl. #
BA Planning Terms
Definition
26
Change management
Planned activities, tools, and techniques to
address the human side of change during a
change initiative, primarily addressing the
needs of the people who will be most affected
by the change.
27
Change team
A cross-functional group of individuals who are
mandated to implement a change.
28
CMMI
Capability maturity model Integration - A
model developed by Software Engineering
Institute
29
Complexity
Indicates implementation difficulty, often
indicated by qualitative scales based on
number of interfaces, complexity of essential
processes, or the number and nature of
resources required
30
Conceptual thinking
Ability to sieved through lots of data and to
find the link connecting them all and thereby fit
them into a larger context
31
Constraints
Constraints are aspects that cannot be changed
by the solution or design It can be restrictions
on budget, time, resources, technology,
infrastructure, policies etc.
32
Consulted
Stakeholder or stakeholder group who will can
be asked for opinions or information about the
task SMEs are generally considered for this
33
Context
The circumstances that influence, are
influenced by, and provide understanding of
the change.
34
Core concept (business
analysis)
One of six ideas that are fundamental to the
practice of business analysis - Change, Need,
Solution, Context, Stakeholder, and Value.
35
Creative thinking
To come up with new ideas, approaches,
alternatives
36
Customer
A stakeholder who uses or may use products or
services produced by the enterprise and may
have contractual or moral rights that the
enterprise is obliged to meet.
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 12 of 114
Sl. #
BA Planning Terms
Definition
37
Decision making
Making a decision by choosing the most
appropriate solution
38
Decomposition
A technique that subdivides a problem into its
component parts in order to facilitate analysis
and understanding of those components.
39
Delphi Estimation
Uses a combination of expert judgment and
history Include individual estimates, sharing the
estimates with experts and having several
rounds until consensus is reached
40
Domain subject matter
expert
A stakeholder with in-depth knowledge of a
topic relevant to the business need or solution
scope.
41
Domain subject matter
expert (SME)
People with in-depth knowledge of a topic
relevant to business need or Solution scope
Examples: Managers, process owners,
consultants etc.
42
Estimate
A quantitative assessment of a planned
outcome, resource requirements, and schedule
where uncertainties and unknowns are
systematically factored into the assessment.
43
Ethics
Ethics is a system of moral principles
44
Function point
Estimation method prepared based on
functionalities of a system
45
Governance approach
Identifies the stakeholders who will take
decisions, set priorities and approve changes to
BA information
46
Identified risks
Risks identified during risk analysis or any other
process
47
Implementation SME
Has specialized knowledge pertaining to
implementation of solution components
Examples: change manager, solution architect,
information architect etc.
48
Implementation subject
matter expert
A stakeholder who has specialized knowledge
regarding the implementation of one or more
solution components.
49
Increase
Decide to take on more risk to pursue an
opportunity
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 13 of 114
Sl. #
BA Planning Terms
Definition
50
Information management
approach
Defines how BA information will be stored,
accessed and utilized during and after the
change is complete
51
Informed
Stakeholder or stakeholder group who is kept
up to date on the task and informed of its
outcome
52
Interface
A shared boundary between any two persons
and/or systems through which information is
communicated.
53
Interface analysis
Interface analysis identifies interfaces and
interactions between solutions and/or solution
components
54
Iteration (business analysis)
A single instance of progressive cycles of
analysis, development, testing, or execution.
55
Key performance indicator
A key performance indicator (KPI) is one that
measures progress towards a strategic goal or
objective
56
Knowledge area (business
analysis)
An area of expertise that includes several
specific business analysis tasks.
57
Knowledge areas
Knowledge areas represent areas of specific BA
expertise
58
Leadership and influencing
Skills involving motivating people to work
together, inspiring them to transform vision
into reality, reducing resistance to changes,
building consensus etc.
59
Learning and Growth
Dimension
Measures regarding employee training and
learning, product and service innovation and
corporate culture
60
Listening
Giving the speaker complete attention and also
interpreting and responding appropriately
61
Market oriented structure
Organizational structure where staff are aligned
to market segments
62
Measurable
Can be quantitatively measured
63
Methodology
A body of methods, techniques, procedures,
working concepts, and rules used to solve a
problem
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 14 of 114
Sl. #
BA Planning Terms
Definition
64
Methodology knowledge
Methodologies determine how a change is
approached and managed Awareness of a
variety of methodologies help Business analysts
to quickly adapt and perform in changing
environments
65
Metric
A quantifiable level of an indicator measured at
a specified point in time.
66
Metrics and key
performance indicators
(KPIs)
Helps in determining whether the desired
future state has been achieved
67
Metrics and KPIs
Metrics and KPIs measure the performance of
solutions, solution components and other
matters of interest to stakeholders
68
Mitigate
Reduce risk probability or the possible negative
consequences
69
Need
A problem or opportunity to be addressed.
70
Non-Verbal communication
Facial expressions, gestures, posture, eye
contact
71
Onion diagram
Indicates level of stakeholder involvement with
the solution and which stakeholder directly
interacts with the solution or participate in a
business process
72
Organization knowledge
Understanding of the organization's operations
73
Organizational model
is a visual representation of the organizational
unit
74
Parametric estimation
Uses a calibrated parametric model of the
element attributes For example, if one use case
takes 24 hours to develop, it will take 480 hours
for developing 20 use cases
75
Personal accountability
Includes effective planning of BA work to
achieve targets and goals by completing tasks
on time and meeting expectations of
stakeholders and colleagues
76
PERT
PERT value (Optimistic + Pessimistic + (4 times
Most Likely))/6
77
Plan
A detailed scheme for doing or achieving
something
78
Planning poker
An agile approach in estimating stories
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 15 of 114
Sl. #
BA Planning Terms
Definition
79
Predictive approach
An approach where planning and baselines are
established early in the life cycle of the
initiative in order to maximize control and
minimize risk.
80
Predictive approach
An approach to deliver functionalities in narrow
slices
81
Product backlog
A set of user stories, requirements, or features
that have been identified as candidates for
potential implementation, prioritized, and
estimated.
82
Project manager
Responsible for managing the work required to
deliver a solution
83
Project scope
The work that must be performed to deliver a
product, service, or result with the specified
features and functions.
84
RACI
RACI (Responsible, Accountable, Consulted and
Informed) matrix, or specific information
technology system roles and responsibilities
identified in a CRUD (Create, Read, Update and
Delete) matrix
85
RACI matrix
Responsible, accountable, consulted, and
informed matrix
86
Regulator
A stakeholder from outside the organization
who is responsible for the definition and
enforcement of standards.
87
Reporting
Reporting is the process of informing
stakeholders of metrics or indicators in
specified formats and at specified intervals
88
Requirements allocation
The process of assigning requirements to be
implemented by specific solution components.
89
Requirements management
plan
Tools, activities, and roles and responsibilities
used on the initiative to manage the
requirements.
90
Responsible
Those who will be performing the work on the
task
91
Risk analysis results
Risks identified as critical for achieving desired
outcome should be addressed
92
Risk assessment
Identifying, analyzing and evaluating risks.
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 16 of 114
Sl. #
BA Planning Terms
Definition
93
Risk register
A register to maintain risks
94
Rolling Wave
Rolling wave technique involves continual
refinement of estimates Estimate the details for
activities in the current iteration or increment
and extrapolate it for the entire scope of work
95
Rough order of magnitude
(ROM)
Based on limited information, a high level
estimate with a very wide confidence interval
96
Scope model
A model that defines the boundaries of a
business domain or solution.
97
Service (business analysis)
The performance of any duties or work for a
stakeholder, from the perspective of the
stakeholder.
98
Solution knowledge
Experience dealing with commercially available
solutions or suppliers can help Business
analysts to evaluate possible alternatives and
improve an existing solution
99
Sponsor
Manages scope and budget
100
Sprint backlog
Backlog items selected for a Sprint
101
Sprint plan
Planned activities for a sprint
102
Stakeholder
A group or individual with a relationship to the
change, the need, or the solution.
103
Stakeholder analysis
Identifying and analyzing the stakeholders who
may be impacted by the change and assess
their impact, participation, and needs
throughout the business analysis activities.
104
Stakeholder analysis results
Understand stakeholders who need to
contribute for understanding and analysis of
the current state
105
Stakeholder list
A catalogue of the stakeholders affected by a
change
106
Stakeholder map
Represent the relationship of stakeholders to
the solution and to one another 2 common
forms of stakeholder maps are:
107
Stakeholder matrix
Maps level of stakeholder influence against
level of stakeholder interest/impact on
stakeholders
108
Stakeholder proxy (business
analyst)
The role a business analyst takes when
representing the needs of a stakeholder or
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 17 of 114
Sl. #
BA Planning Terms
Definition
stakeholder group.
109
Stakeholders
Any person or group or organization affected
by the change or has ability to affect the
change
110
Story point
An agile estimation method
111
Supplier
Uutside the boundary of a given organization
112
Tailor
Modify methodology to suit the context
113
Task (business analysis)
A discrete piece of work that may be
performed formally or informally as part of
business analysis.
114
Teaching
Through teaching, BAs utilize different
methods to communicate information,
concepts, ideas and issues to stakeholders and
ensure that they are understood by them
115
Technique
A manner, method, or style for conducting a
business analysis task or for shaping its output.
116
Tester
An individual responsible for determining how
to verify that the solution meets the
requirements defined by the business analyst,
and conducting the verification process.
117
Time-box
An agreed-upon period of time in which an
activity is conducted or a defined deliverable is
intended to be produced.
118
Top-down estimation
Estimate efforts for components using
hierarchical breakdown
119
Transfer
Liability for dealing with the risk is moved to, or
shared with, a third party
120
Trustworthiness
Timely delivery of tasks, honesty, consistency
and confidence
121
Value (business analysis)
The worth, importance, or usefulness of
something to a stakeholder in a context.
122
Velocity
Number of stories implemented per sprint
123
Work breakdown structure
Decomposes project scope in phases, work
packages and deliverables
124
Work breakdown structure
(WBS)
A deliverable-oriented hierarchical
decomposition of the work to be executed
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 18 of 114
Knowledge Area 2 – Elicitation and Collaboration
Sl. #
Elicitation & Collab. Terms
Definition
1
Active / Noticeable
observation
Observer asks questions during the process
May interrupt the work flow but helps in
gaining a quick understanding
2
Affinity map
A technique to put related concepts
together
3
Artifact (business analysis)
Any solution-relevant object that is created
as part of business analysis efforts.
4
Assumption
An influencing factor that is believed to be
true but has not been confirmed to be
accurate, or that could be true now but may
not be in the future.
5
Atomic
At lowest level
6
Author
Creator of requirements
7
Availability
Extent to which solution is operable and
accessible when required
8
Behavioral rules
Behavioral rules intend to guide the actions
of people working within the organization,
or people who interact with it
9
Behavioural business rule
Related to conduct, action, practice, or
procedure
10
Brainstorming
A team activity that seeks to produce a
broad or diverse set of options through the
rapid and uncritical generation of ideas.
11
Business analysis
information
Any kind of information at any level of detail
that is used as an input to business analysis
work, or as an output of business analysis
work.
12
Business analysis package
A document, presentation, or other
collection of text, matrices, diagrams and
models, representing business analysis
information.
13
Business capabilities
Describe the ability of an enterprise to act
on or transform something that helps
achieve a business goal or objective
14
Business policy
A non-practicable directive that controls
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 19 of 114
Sl. #
Elicitation & Collab. Terms
Definition
and influences the actions of an enterprise.
15
Business process
An end-to-end set of activities
16
Business requirement
A representation of goals, objectives and
outcomes that describe why a change has
been initiated and how success will be
assessed.
17
Business requirements
Goals, objectives and outcomes which
indicate the reason for initiating a change
18
Business rule
A specific, practicable, testable directive that
is under the control of the business and that
serves as a criterion for guiding behaviour,
shaping judgments, or making decisions.
19
Closed questions
Respondents select from available
responses Typically Yes/No, multiple-choice,
rank order decision etc
20
Collaboration
The act of two or more people working
together towards a common goal.
21
Collaboration
Act of working together with other people
towards accomplishing a common goal
22
Collaboration and
Knowledge Management
Tools
Capture organization wide knowledge and
makes it available and accessible to the
entire team
23
Collaborative games
Collaborative games use game playing
techniques to collaborate in developing
common understanding of a problem or a
solution
24
Communication Tools
(Email, instant messaging)
Facilitates long distance communication
25
Compatibility
Ability to co-exist and interact with other
applications
26
Compliance
Legal, financial or regulatory constraints
which can differ based on the scenario
27
Corrective action
Establish ways to reduce the negative
impact of an event
28
Decision requirements
diagram
Shows information, knowledge and decision
making involved in a more complex
business decision
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 20 of 114
Sl. #
Elicitation & Collab. Terms
Definition
29
Definitional business rule
A rule that indicates something is
necessarily true (or untrue); a rule that is
intended as a definitional criterion for
concepts, knowledge, or information. Also
known as a structural rule.
30
Definitional rules
Rules representing operational knowledge
of the organization They prescribe how
information may be derived, inferred or
calculated based on information available to
the business
31
Deliverable
Any unique and verifiable work product or
service that a party has agreed to deliver.
32
Document analysis
Elicit business analysis information, by
examining materials which describe about
the business environment or organizational
assets
33
Document analysis
(business analysis)
An examination of the documentation of an
existing system in order to elicit
requirements.
34
Domain
The sphere of knowledge that defines a set
of common requirements, terminology, and
functionality for any program or initiative
solving a problem.
35
Domain knowledge
Knowledge of and expertise in the business
domain
36
Elicitation
Iterative derivation and extraction of
information from stakeholders or other
sources.
37
Elicitation
Practice of collecting requirements from
stakeholders or other sources
38
Elicitation activity plan
Plan to guide sources, schedule of elicitation
39
Elicitation and collaboration
Tasks BAs carry out to Prepare for
elicitation, Conduct elicitation activities,
confirm results, communicate and
collaborate with stakeholders
40
Existing Business analysis
information
Provide better understanding of the goals
of elicitation activity and help in preparing
for elicitation
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 21 of 114
Sl. #
Elicitation & Collab. Terms
Definition
41
Experiment
Elicitation performed in a controlled manner
to make a discovery, test a hypothesis, or
demonstrate a known fact.
42
Extensibility
Whether the solution is able to incorporate
new functionality
43
Facilitation
The art of leading and encouraging people
through systematic efforts toward agreed-
upon objectives in a manner that enhances
involvement, collaboration, productivity,
and synergy.
44
Feature
A distinguishing characteristic of a solution
that implements a cohesive set of
requirements and which delivers value for a
set of stakeholders.
45
Fish-bowl
A technique in which one group presents
and other group critically observe the group
46
Focus group
A group formed to to elicit ideas and
attitudes about a specific product, service,
or opportunity
47
Focus groups
Focus groups elicit ideas, and attitudes from
pre-qualified individuals about a specific
product, service or opportunity in an
interactive group environment
48
Functional decomposition
Breaks down a large aspect (processes,
functional areas, deliverables, scope, or
problems) into smaller aspects, as
independent as possible, so that work can
be assigned to different groups
49
Functional requirement
A capability that a solution must have in
terms of the behaviour and information the
solution will manage.
50
Functionality
Extent to which user needs are met by the
solution functions
51
Glossary
Comprises of key terms relevant to a
business domain in order to provide a
common understanding of terms
52
Group collaboration
To communicate the package to a group of
relevant stakeholders at the same time
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 22 of 114
Sl. #
Elicitation & Collab. Terms
Definition
53
Heterogeneous group
When the group has dissimilar
characteristics
54
Homogeneous group
When the group has similar characteristics
55
Individual collaboration
To communicate the package to one
stakeholder at a time
56
Industry knowledge
Understanding of the current practices and
activities with an industry
57
Input (business analysis)
Information consumed or transformed to
produce an output. An input is the
information necessary for a task to begin.
58
In-scope
Elements contained by the boundary (as
seen from inside) E.g. Functional
decomposition
59
Interoperability
Ability of systems to communicate by
exchanging data or services.
60
Interview
Eliciting information from a person or group
of people in an informal or formal setting by
asking relevant questions and recording the
responses.
61
Interviews
Interviews are a common form of elicitation
technique where interviewers ask questions
to stakeholders
62
Knowledge Sources
Original source documents or people from
which the necessary decision logic can be or
has been derived.
63
Localization
Requirements which deal with local
languages, laws, currencies, cultures,
spellings etc
64
Maintainability
Ability to change one component without
affecting others and without causing
unexpected failures, ability to re-use
components and testability
65
Non-functional requirement
Describes the performance or quality
attributes a solution must meet.
66
Non-functional
requirements
Non-functional requirements (NFRs)
analysis examines the requirements for a
solution that define how well the functional
requirements MUST perform
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 23 of 114
Sl. #
Elicitation & Collab. Terms
Definition
67
Observation
To elicit information by observing activities
and their context
68
Observation (business
analysis)
Studying and analyzing one or more
stakeholders in their work environment in
order to elicit requirements.
69
Open ended questions
Questions which can have descriptive
answer
70
Operational support
A stakeholder who is responsible for the
day-to-day management and maintenance
of a system or product.
71
Organization modelling
The analysis technique used to describe
roles, responsibilities and reporting
structures that exist within an enterprise.
72
Organizational structure
describes the formal relationships between
people working in the enterprise
73
Organizational unit
Any recognized association of people within
an organization or enterprise.
74
Out-of-scope
Elements not contained within the boundary
(as seen from outside) E.g. Context diagram
75
Passive/Unnoticeable
observation
Observer asks questions at the end and
does not cause interruption to work
76
Persona
Persona is a fictional character or model
that depicts the way a typical user interacts
with a product
77
Portability
How easy it is to transfer a solution or
component from one environment to
another
78
Process model
A set of diagrams and supporting
information about a process and factors
that could influence the process. Some
process models are used to simulate the
performance of the process.
79
Product box
A dummy boX showing product features
80
Proof of Principle or
Concept
Created to validate the system design
without modelling appearance, materials
used etc
81
Questionnaire
A set of defined questions, with a choice of
answers, used to collect information from
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 24 of 114
Sl. #
Elicitation & Collab. Terms
Definition
respondents.
82
Reliability
Measure of application being available
when needed Includes ability of the
application to recover from errors, uptime,
or failures in interfaces
83
Requirement
A usable representation of a need.
84
Requirements artifact
A business analysis artifact containing
information about requirements such as a
diagram, matrix, document or model.
85
Requirements package
A specialized form of a business analysis
package primarily concerned with
requirements. A requirements package may
represent a baseline of a collection of
requirements.
86
Requirements workshop
A structured meeting in which a carefully
selected group of stakeholders collaborate
to define and/or refine requirements under
the guidance of a skilled neutral facilitator.
87
Roles and permissions
matrix
Roles and permissions matrix ensures
coverage of activities by denoting
responsibility, to identify roles, to discover
missing roles and to communicate results of
a planned change
88
Rules engine
A centralized system to manage business
rules
89
Scalability
Extent to which a solution is able to evolve
to handle increased amounts of work
90
Scope
The boundaries of control, change, a
solution, or a need.
91
Secondary research
Obtaining data from secondary sources
such as internet or published databases
92
Security
Ability to ensure appropriate confidentiality
and integrity of information, to verify when
actions were taken and by whom and to
authenticate users
93
Service Level Agreements
Organization constraints which are agreed
upon by the provider and user of the
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 25 of 114
Sl. #
Elicitation & Collab. Terms
Definition
solution
94
Solution requirement
A capability or quality of a solution that
meets the Stakeholder requirements.
95
Solution requirements
Capabilities and qualities of a solution that
meets stakeholder requirements Broadly
classified into - Functional requirements,
Non-functional requirements or quality of
service requirements
96
Specific
Something with an observable outcome
97
Stakeholder collaboration
approach
A high level plan to collaberate with
stakeholders
98
Stakeholder collaboration
plan
A plan created to enable stakeholder
colaberation
99
Stakeholder requirement
A description of the needs of a particular
stakeholder or class of stakeholders
100
Stakeholder requirements
Stakeholder needs which must be met to
achieve business requirements
101
Stated requirement
A requirement articulated by a stakeholder
that has not been analyzed, verified, or
validated. Stated requirements frequently
reflect the desires of a stakeholder rather
than the actual need.
102
Story boarding
Visually and textually details the sequence
of activities
103
Supporting materials
Any materials, information, tools, or
equipment to Prepare for elicitation, or use
during the elicitation
104
Survey
Collecting and measuring the opinions or
experiences of a group of people through a
series of questions.
105
Template Architectures
An architectural framework is a collection of
viewpoints that is standard across an
industry, sector or organization
106
Time-bound
Has a defined timeframe consistent with the
business need
107
Transition requirement
Conditions the solution must meet to
facilitate transition from the current state to
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 26 of 114
Sl. #
Elicitation & Collab. Terms
Definition
the future state
108
Usability
How easy it is for a user to learn how to use
the solution
109
Verbal communication
Speaker uses spoken words to convey BA
information, ideas, concepts, facts and
opinions to the receiver
110
Viewpoint
A set of conventions that define how
requirements will be represented, how these
representations will be organized, and how
they will be related.
111
Viewpoints
What information should be provided to
each stakeholder group
112
Views
Views describe actual requirements and
designs that are produced A collection of
views makes up the Requirements
architecture for a specific solution
113
Visual thinking
Graphical representations help to
communicate complex concepts and
models to stakeholders and thereby help
them understand and engage in the
concepts that are being presented
114
Work product (business
analysis)
A document or collection of notes or
diagrams used by the business analyst
during the requirements development
process.
115
Workshop
A facilitated and focused event attended by
key stakeholders for the purpose of
achieving a defined goal.
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 27 of 114
Knowledge Area 3 – Requirements Life Cycle Management
Sl. #
Req. LCM Terms
Definition
1
Absolute reference
Unique numeric (preferred) or textual
identifier – Not to be altered or re-used
even if the requirement is moved,
changed or deleted
2
Accept
Decide not to do anything about the risk
If the risk does occur, a workaround will
be developed at that time
3
Acceptance criteria
Criteria associated with requirements,
products, or the delivery cycle that must
be met in order to achieve stakeholder
acceptance.
4
Backlog management
Refers to the planned approach manage
remaining work for the project
5
Benefit as a basis for
prioritization
Benefit attained on implementing
requirements in terms of functionality,
desired quality, Business objectives etc
Requirements that provide highest benefit
are prioritized first
6
Change control
Controlling changes to requirements and
designs so that the impact of requested
changes is understood and agreed-to
before the changes are made.
7
Cost as a basis for
prioritization
Effort and resources required to
implement a requirement Requirements
priority may change based on the cost
8
Delegations
Identify which authorities can be
delegated by one individual to another on
a short-term or permanent basis
9
Dependencies as a basis for
prioritization
When one requirement cannot be fulfilled
unless the other requirement is fulfilled
10
Depends relationship
One requirement can be implemented
only if the other has been implemented or
easier to implement if the other is
implemented
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 28 of 114
Sl. #
Req. LCM Terms
Definition
11
Derive relationship
When one requirement is derived from
the other (Solution requirements are
derived from stakeholder requirements
12
Evaluation criteria
Defines a set of measures to rank multiple
solutions options, solutions or solution
components based on their value for
stakeholders
13
Governance process
(change)
A process by which appropriate decision
makers use relevant information to make
decisions regarding a change or solution,
including the means for obtaining
approvals and priorities.
14
Impact analysis
An assessment of the effects a proposed
change will have on a stakeholder or
stakeholder group, project, or system.
15
Lessons learned
Also known as retrospective
16
Lessons learned process
A process improvement technique used to
learn about and improve process
17
Life cycle
A series of changes an item or object
undergoes from inception to retirement
18
Monitoring
Collecting data on a continuous basis
from a solution in order to determine how
well a solution is implemented compared
to expected results. See also metric;
indicator.
19
Multi-phased prioritization
approach
Prioritization done multiple times where
the prioritization basis can be different
20
Negotiation and conflict
resolution
These skills involve mediating discussions
between stakeholders and team members
to resolve difference of opinions arising
from different points of view and help
them arrive at a common consensus
21
Neutrality
A neutral approach to risk means that the
probable benefits gained from the risk
response must equal or outweigh the
costs in order to justify action
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 29 of 114
Sl. #
Req. LCM Terms
Definition
22
Ownership
individual or group that needs the
requirement, or will be the business owner
after the project is released into target
environment
23
Penalty as a basis for
prioritization
Consequences resulting from not
implementing a requirement It may also
be negative, that is, not satisfying
customer needs
24
Prioritization
Determining the relative importance of a
set of items in order to determine the
order in which they will be addressed.
25
Priority
Requirements need to be implemented
first
26
Regulatory or Policy
Compliance as a basis for
prioritization
These requirements take precedence over
stakeholder interests as regulatory and
policy demands are mandatory They
cannot be overlooked
27
Repository
A real or virtual facility where all
information on a specific topic is stored
and is available for retrieval.
28
Requirements (traced)
Requirements for which relationships to
other requirements, solution components,
or releases, phases, or iterations are
established
29
Requirements architecture
The requirements of an initiative and the
interrelationships between these
requirements.
30
Requirements attribute
A characteristic or property of a
requirement used to assist with
requirements management.
31
Requirements life cycle
The stages through which a requirement
progresses from inception to retirement.
32
Requirements life cycle
management
Tasks BAs perform to manage and
maintain requirements and design
information from start till end
33
Requirements life cycle
management tools
Tools that facilitate recording, organizing,
storing and sharing requirements and
designs
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 30 of 114
Sl. #
Req. LCM Terms
Definition
34
Requirements management
Planning, executing, monitoring, and
controlling any or all of the work
associated with requirements
35
Requirements management
tool
Tool to manage requirements
36
Requirements management
tools/repository
Tools to store and manage BA information
37
Requirements traceability
To link requirements
38
Residual risk
The risk remaining after action has been
taken or plans have been put in place to
deal with the original risk.
39
Risk
Effect of uncertainty on the value of a
change, solution or enterprise BAs
identify, prioritize and mitigate risks by
collaborating with stakeholders
40
Risk (business analysis)
The effect of uncertainty on the value of a
change, a solution, or the enterprise. See
also residual risk.
41
Risk as a basis for
prioritization
Chances that a requirement cannot deliver
Potential value or get fulfilled due to
factors like difficulty in implementation,
rejection from stakeholders etc
42
Risks as basis for
prioritization
associated with meeting, or not meeting
the requirement
43
Satisfy relationship
Relationship between an implementation
element and the requirements it is
satisfying
44
Stability
Maturity
45
Stability as a basis for
prioritization
Requirements with less stability have low
priority It means the requirement can
change upon further analysis and
stakeholder consensus
46
Status
Indicates whether requirement is
proposed, accepted, verified, postponed,
cancelled, or implemented
47
Time Sensitivity as a basis
for prioritization
The date after which the implementation
of a requirement loses value considerably
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 31 of 114
Sl. #
Req. LCM Terms
Definition
48
Traceability
Ability to look at a requirement and
others to which it is related, linking
business requirements to stakeholder and
solution requirements, to artifacts and to
solution components
49
Traceability Repositories
A tool or manual approach to maintain
requirements traceabilities
50
Trade-off
Accept a compromise on a feature based
on resource constraints
51
Urgency
indicates how soon the requirement is
needed It is necessary to specify this
separately from priority when a deadline
exists for implementation
52
User story
A small, concise statement of
functionality or quality needed to deliver
value to a specific stakeholder.
53
Validate relationship
A relation between a requirement and its
test case to validate whether the solution
fulfills the requirement
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 32 of 114
Knowledge Area 4 – Strategy Analysis
#
Strategy Analysis Terms
Definition
1
Architecture
Design, structure, and behaviour of the
current and future states
2
AS IS
The current state
3
Background research
Research gathered through document
analysis comprises of reviewing materials
like marketing studies, industry standards,
guidelines etc
4
Balance score card
A strategic planning and management tool
to measure organizational performance
beyond traditional financial measures
5
Benchmark studies
Benchmark studies are conducted to
compare organizational practices against
the best-in-class practices from competitor
enterprises, in government, or from industry
associations or standards
6
Benchmarking
A comparison of a decision, process, service,
or system's cost, time, quality, or other
metrics to those of leading peers to identify
opportunities for improvement.
7
Business architecture
Design, structure, and behaviour of the
current and future states of an enterprise
8
Business architecture
Describes key elements of current state
9
Business case
A justification for a course of action based
on the benefits and costs
10
Business decision
A decision that can be made based on
strategy, executive judgment, consensus,
and business rules, and that is generally
made in response to events or at defined
points in a business process.
11
Business goal
A state or condition that an organization is
seeking to establish and maintain, usually
expressed qualitatively rather than
quantitatively.
12
Business model canvas
A business model canvas is comprised of
nine building blocks that describe how an
organization intends to deliver value
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 33 of 114
#
Strategy Analysis Terms
Definition
13
Business need
A problem or opportunity of strategic or
tactical importance to be addressed.
14
Business objective
An objective, measurable result to indicate
that a business goal has been achieved.
15
Business objectives
Desired business benefits
16
Business problem
An issue of strategic or tactical importance
preventing an enterprise or organization
from achieving its goals.
17
Capability
The set of activities the enterprise performs,
the knowledge it has, the products and
services it provides, the functions it
supports, and the methods it uses to make
decisions.
18
Capability centric view
Come up with innovative solutions by
combining existing capabilities
19
Capability maps
Provide a graphical view of elements
involved in business capability analysis
20
Change
The act of transformation in response to a
need.
21
Change agent
One who is a catalyst for change.
22
Change approach
High level plan to achieve the change
23
Change strategy
A plan to move from the current state to
the future state to achieve the desired
business objectives.
24
Channels
Channels are the different ways an
enterprise interacts with and delivers value
to its customers
25
Competitive analysis
A structured assessment which captures the
key characteristics of an industry to predict
the long-term profitability prospects and to
determine the practices of the most
significant competitors.
26
Core capabilities
Activities or essential functions in an
enterprise that differentiates it from others
27
Cost of the Change
Expected cost of building or acquiring the
solution components and costs of
transitioning
28
Cost structure
Elements of costs for any change or product
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 34 of 114
#
Strategy Analysis Terms
Definition
or service
29
Cost-benefit analysis
An analysis which compares and quantifies
the financial and non-financial costs of
making a change or implementing a
solution compared to the benefits gained.
30
Customer Dimension
Measures on customer focus, satisfaction
and delivery of value
31
Customer segments
Customer segments group customers with
common needs and attributes so that the
enterprise can more effectively and
efficiently address the needs of each
segment
32
Discount Rate
Assumed interest rate + risk premium
33
Enterprise
A system of one or more organizations and
the solutions they use to pursue a shared
set of common goals.
34
Enterprise architecture
A description of the business processes,
information technology, people, operations,
information, and projects of an enterprise
and the relationships between them.
35
Evaluation
Systematic and objective assessment of a
solution
36
Expected benefits
Positive value that a solution
37
Expected Costs
Comprises of costs to acquire a solution,
negative effects it may have on
stakeholders and costs to maintain it over
time
38
Feasibility study
To determine if they are technically,
organizationally, and economically possible
within the constraints of the enterprise, and
whether they will deliver the desired
benefits to the enterprise.
39
Functionally oriented
structure
Functionally oriented organizations groups
staff together based on shared skills or
areas of expertise
40
Future state description
Desired future state and expected value
delivery
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 35 of 114
#
Strategy Analysis Terms
Definition
41
Gap analysis
A comparison of the current state and
desired future state of an enterprise in
order to identify differences that need to be
addressed.
42
Goals
Long-term, on-going and qualitative
statements of a condition that the
organization seeks to establish and
maintain For example: We want to be most
preferred technology partner to our clients
43
Initiative
A specific project, program, or action taken
to solve some business problem(s) or
achieve some specific change objective(s).
44
Internal Rate of Return
Discount rate at which a NPV becomes 0
45
Leasing
Customer has temporary rights to use an
asset
46
Lending
Customer has temporary rights to use an
asset
47
Licensing or Subscription fees
Customer pays for the right to access a
particular asset, either as a one-time fee or
as a recurring cost
48
Market analysis
Researching customers to determine the
products and services
49
Matrix
A textual form of modelling used to
represent information that can be
categorized, cross-referenced, and
represented in a table format.
50
Matrix structure
In matrix model, there are separate
managers for each functional area, and for
each product, service, or customer group
51
Mission statement
A formal declaration of values and goals
that expresses the Core purpose of the
enterprise.
52
Net Present Value
Net present value (NPV) is the present value
of the benefits minus the original cost of
the investment Net Present Value = Present
Value – Cost of Investment
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 36 of 114
#
Strategy Analysis Terms
Definition
53
Objectives
Descriptive, granular, specific and linked to
measures to objectively assess if the
objective has been achieved
54
Opportunities (External)
External factors that the assessed group can
take advantage of such as new markets,
new technology, changes in the competitive
marketplace, or other forces
55
Opportunity costs
Opportunity costs describe the benefits that
could have been attained by taking an
alternative design option
56
Organization
An autonomous group of people under the
management of a single individual or
board, that works towards common goals
and objectives.
57
Organizational capability
A function inside the enterprise, made up of
components such as processes,
technologies, and information and used by
organizations to achieve their goals.
58
Organizational strategy
Set of goals and objectives which guides
operations, establishes direction and
provides a vision for the future state Can be
explicit or implicit
59
Payback Period
Time period required to generate enough
benefits to recover the cost of the change
60
Present Value
Present Value = Sum of (Net Benefits in that
period / (1 + Discount Rate for that period))
for all periods in the cost-benefit analysis
61
Primary research
Use primary research such as surveys,
interviews, or direct observations if
necessary
62
Process
A set of activities designed to accomplish a
specific objective by taking one or more
defined inputs and turning them into
defined outputs.
63
Process centric view
Used to look for ways to enhance the
performance of present activities
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 37 of 114
#
Strategy Analysis Terms
Definition
64
Product vision statement
A brief statement or paragraph that
describes the goals of the solution and how
it supports the strategy of the organization
or enterprise.
65
Project
A temporary endeavour undertaken to
create a unique product, service, or result.
66
Renting
Customer has temporary rights to use an
asset
67
Return on Investment
Net benefits * 100 / Cost of the change
68
Return on investment (ROI)
(business analysis)
A measure of the profitability of a project or
investment.
69
Revenue stream
A revenue stream is a way or method by
which revenue comes into an enterprise
from each customer segment in exchange
for the realization of a value proposition
70
Revenue thorough sales
the customer is granted ownership rights to
a specific product
71
Risk-seeking
Willingness to accept relatively high risks in
order to maximize the potential benefit
Risk-seekers may accept low chances of
success if the benefits of success are higher
72
Solution component
A sub-part of a solution that can be people,
infrastructure, hardware, software,
equipment, facilities, and process assets or
any combination of these sub-parts.
73
Strategy
A description of the chosen approach to
apply the capabilities of an enterprise in
order to reach a desired set of goals or
objectives.
74
Strategy analysis
Tasks BAs perform to identify a need of
strategic or tactical importance, how to
collaborate and enable stakeholders to
address that need etc
75
Strengths (Internal)
Anything that the assessed group does well
such as experienced personnel, effective
processes, IT systems, customer
relationships, or any other internal factor
that leads to success
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 38 of 114
#
Strategy Analysis Terms
Definition
76
Strengths, weaknesses,
opportunities, and threats
analysis (SWOT)
An analysis model used to understand
influencing factors and how they may affect
an initiative. Also known as SWOT analysis.
77
System
A set of interdependent components that
interact in various ways to produce a set of
desired outcomes.
78
Systems thinking
Understanding the enterprise from a holistic
view by learning how people, process and
technology interact
79
Threats (External)
External factors that can negatively affect
the assessed group such as a new
competitor, economic downturns, or other
forces Threats are also outside of the
group’s control
80
TO BE
The desired future state
81
Total Cost of Ownership
(TCO)
Cost of change + Usage cost + Support
cost for a period
82
Transaction or Usage fees
the customer pays each time they use a
good or service
83
Value Proposition
A value proposition represents what a
customer is willing to exchange for having
their needs met
84
Value-add
characteristics, features, and business
activities for which the customer is willing to
pay
85
Weaknesses (Internal)
Things that the assessed group does poorly
or not at all such as not having market
access
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 39 of 114
Knowledge Area 5 – Requirements Analysis and Design Definition
Sl. #
RADD Terms
Definition
1
Activity diagram
Activity diagram uses swim-lanes to show
responsibilities, synchronization bars to
show parallel processing and multiple
exit decision points
2
Actor (business analysis)
A human, device, or system that plays
some specified role in interacting with a
solution.
3
Ad hoc review
Informal review or assistance from a peer
4
Alternative flow
Other paths that may be followed to
achieve an actor’s goal
5
Architecture management
software
Modelling softwares help in managing
volume, complexity and versions of the
relationships within the Requirements
architecture
6
Associations
Relationships
7
Asynchronous call
Allows the object to continue with its
own processing after sending the signal
8
Attribute
Attributes define particular piece of
information associated with an entity
9
Basic, primary or main success
flow
Shortest or simplest successful path to
achieve an actor’s goal
10
BPMN
BPMN is an industry-standard that is
accessible by both business users and
technical developers
11
Business non-value-add
Characteristics that must be included in
the offering, activities performed to meet
regulatory and other needs, or costs
associated with doing business, for which
the customer is not willing to pay
12
Business process management
(BPM)
A management discipline that determines
how manual and automated processes
are created, modified, cancelled, and
governed.
13
Business process re-
engineering
Rethinking and redesigning business
processes to generate improvements in
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 40 of 114
Sl. #
RADD Terms
Definition
performance measures.
14
Business rules analysis
Business rules analysis is used to identify,
express, validate, refine, and organize the
rules that shape day-to-day business
behavior
15
Cardinality
Term cardinality is to refer to the
minimum and maximum number of
occurrences to which an entity related.
16
Cardinality
Term cardinality is to refer to the
minimum and maximum number of
occurrences to which an entity related
17
Class
An entity in object model
18
Class diagram
A diagram showing classes and their
relationships
19
Concept model
An analysis model that develops the
meaning of core concepts for a domain
20
Concept models
Concept models organize business
vocabulary, usually starting with glossary
21
Conceptual data model
Independent of any solution To represent
how business perceives its information
22
Crow's Foot Notation
A notation for ER diagram
23
CRUD matrix
Create, Retrieve, Update, Delete
24
Data mining
Data mining, an approach to document
analysis is to analyze data to group it into
categories, determine patterns and
opportunities for change
25
Decision analysis
An approach to decision making that
examines and models the possible
consequences of different decisions, and
assists in making an optimal decision
under conditions of uncertainty.
26
Decision modelling
Decision modelling shows how
repeatable business decisions are made
using data and knowledge for any
decision, simple or complex
27
Decision table
A decision table is a compact, tabular
representation of a set of these rules
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 41 of 114
Sl. #
RADD Terms
Definition
28
Deployment model
Shows how computing aspects are
distributed
29
Design
A usable representation of a solution. For
more information see Key Terms (p. 14)
and Requirements and Designs (p. 19).
30
Design options
Describe different ways to satisfy
business needs Options come with their
own set of change challenges and risks
31
Desk Check
Informal technique where a reviewer who
was not involved in creation of the work
product provides a feedback
32
Dynamic systems development
method (DSDM)
A project delivery framework which
focuses on fixing cost, quality, and time
at the beginning while contingency is
managed by varying the features to be
delivered.
33
Entity
Anything of interest to business domain
from data perspective
34
Entity relationship diagram
A diagram showing entities and their
relationships
35
Entity-relationship diagram
A graphical representation of the entities
relevant to a chosen problem domain
and the relationships between them.
36
Event (business analysis)
An occurrence or incident to which an
organizational unit, system, or process
must respond.
37
Evolutionary or Functional
prototype
Extends the initial interface requirements
into a fully functioning system Requires
specialized prototyping tool or language
and produces a working application
38
Evolutionary prototype
A prototype that is continuously modified
and updated in response to feedback
from stakeholders.
39
Exception flow
If the circumstance does not allow the
actor to achieve their goal, the use case is
considered unsuccessful, and is
terminated
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 42 of 114
Sl. #
RADD Terms
Definition
40
Extend
Allows for the insertion of additional
behaviour into a use case
41
External interface
An interaction that is outside the
proposed solution. It can be another
hardware system, software system, or a
human interaction with which the
proposed solution will interact.
42
Form Study Prototype
Focuses on basic size, look and feel of the
product and not on the functionality
43
Formal Walkthrough (also
known as Team Review)
Technique that uses the individual review
and team consolidation activities
44
Functional Prototype
To test software functionality, qualities of
the system, workflow etc Also referred to
as ‘working model’
45
Gane-Sarson Notation
A DFD notation
46
Hardware
Tools like printers, photocopiers, scanners
allows for replication and distribution of
information
47
Horizontal prototype
A prototype that is used to explore
requirements and designs at one level of
a proposed solution, such as the
customer-facing view or the interface to
another organization.
48
Include
Allows for the use case to make use of
functionality present in another use case
49
Informal Walkthrough
Informal technique conducted when the
work product is in draft state and calls for
feedback
50
Inheritance
Ability to inherit properties of super class
51
Linear and logistic regression
Mathematical modeling done to establish
relationships between variables
52
Logical data model
Incorporates rules of normalization to
formally manage the integrity of the data
and relationships To design a solution
53
Meta data
Data about data
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 43 of 114
Sl. #
RADD Terms
Definition
54
Metadata
A description of data to help understand
how to use that data, either in terms of
the structure and specification of the
data, or the description of a specific
instance of an object.
55
Model
A representation and simplification of
reality developed to convey information
to a specific audience to support analysis,
communication, and understanding.
56
Modelling notations/ standards
Helps requirements and designs to be
precisely specified
57
Modelling tools
Tools that facilitate drawing and storing
matrices and diagrams to represent
requirements
58
Models
Diagrams, matrices, formulas those
abstract and simplify reality in a useful
way
59
Neural networks
A computer system modelled on the
human brain and nervous system.
60
Noun concepts
Entities or objects of interest for e.g.
“Customer”, “Order” etc
61
Online analytical processing
(OLAP)
A business intelligence approach that
allows users to analyze large amounts of
data from different points of view.
62
Paper Prototyping
Interface or process is drafted using
paper and pencil
63
Pass Around
Multiple reviewers provide verbal or
written feedback
64
Peer review
A formal or informal review of a work
product to identify errors or
opportunities for improvement. See also
inspection.
65
Physical data model
Describe how a database is physically
organized It addresses concerns like
performance, concurrency and security
66
Post-condition
Condition achieved after successful
completion of the use-case
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 44 of 114
Sl. #
RADD Terms
Definition
67
Pre-condition
Condition that must exist for the use case
to be initiated
68
Process analysis
Process analysis analyzes processes for
their effectiveness, efficiency and
identifies improvement opportunities
69
Process modelling
Process modelling is a standardized
graphical model to describe the
sequential flow of work or activities
70
Program process flow
A program process flow shows the
sequential execution of program
statements within a software program
71
Proof of concept
A model created to validate the design of
a solution without modelling the
appearance, materials used in the
creation of work, or processes and
workflows ultimately used by the
stakeholders.
72
Prototype
A partial or simulated approximation of
the solution for the purpose of eliciting
or verifying requirements with
stakeholders.
73
Quality
The degree to which a set of inherent
characteristics fulfills needs.
74
Quality assurance
A set of activities performed to ensure
that a process will deliver products that
meet an appropriate level of quality.
75
RDBMS
Relational database management system
76
Requirements analysis and
design definition
Tasks BAs carry out to organize elicited
requirements, model them, validate and
verify them and identify and estimate
Potential value of solution options
77
Requirements model
An abstract (usually graphical)
representation of some aspect of the
current or future state.
78
Requirements validation
Work done to evaluate requirements to
ensure they support the delivery of the
expected benefits and are within the
solution scope.
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 45 of 114
Sl. #
RADD Terms
Definition
79
Requirements verification
Work done to evaluate requirements to
ensure they are defined correctly
80
Reviews
Reviews are performed to communicate,
verify and validate the content of work
products
81
Risk analysis
Identify uncertainties that could
negatively affect value, analyze and
evaluate those uncertainties and develop
and manages way of dealing with the
risks
82
Scenarios and use cases
Scenarios, and use cases describe how a
person or system interacts with a solution
to accomplish one or more of that person
or systems goals
83
Secondary actor
An actor external to the system under
design that supports the execution of a
use case.
84
Sequence diagram
A type of diagram that shows objects
participating in interactions and the
messages exchanged between them.
85
Sequence diagrams
Sequence diagrams (also known as event
diagrams) model logic of usage scenarios
86
Simulation
To demonstrate solutions or solution
components
87
Single Issue Review (also
known as Technical Review)
Focuses on either one issue or a standard
88
Solution option
One possible way to satisfy one or more
needs in a context.
89
State diagram
An analysis model showing the life cycle
of a data entity or class.
90
State models
How that entity changes from one state
to another
91
State table
A state table is a 2-dimensional matrix
showing states and the transitions
between them
92
Support vector machines
Supervised learning models with
associated learning algorithms
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 46 of 114
Sl. #
RADD Terms
Definition
93
Swimlane
A horizontal or vertical section of a
process diagram that shows which
activities are performed by a particular
actor or role.
94
Synchronous call
Synchronous call transfers the control to
the receiving object The sender cannot
act until a return message is received
95
System process model
A system process model defines the
sequential flow of control among
programs or units within a computer
system
96
Temporal event
An event based on time that can trigger
the initiation of a process, evaluation of
business rules, or some other response.
97
Throw-away prototype
A prototype used to quickly uncover and
clarify requirements or designs using
simple tools, sometimes just paper and
pencil. It is intended to be discarded
when the final system has been
developed.
98
Transition requirements
Capabilities that the solution must
possess in order to facilitate transition
from current state to future state
99
Trigger
An event (typically an action taken by a
primary actor) that initiates the flow of
event for a use case
100
UML
Unified Modeling Language
101
Usability Prototype
Model to test how end user interacts with
the system
102
Use case
A description of the observable
interaction between an actor (or actors)
and a solution that occurs when the actor
uses the system to accomplish a specific
goal.
103
Use case diagram
A type of diagram defined by UML® that
captures all actors and use cases involved
with a system or product.
104
Use case point
Estimation prepared on the basis of use
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 47 of 114
Sl. #
RADD Terms
Definition
cases
105
User Stories
User Stories are a brief textual
description, typically 1 or 2 sentences, of
functionality that users need from a
solution to meet a business objective
106
Validated requirement
A requirement that has been reviewed
and is determined to support the delivery
of the expected benefits, and is within the
solution scope.
107
Validation (business analysis)
The process of checking that a
deliverable is suitable for its intended
use. See also requirements validation.
108
Value stream mapping
A complete, fact-based, time-series
representation of the stream of activities
required to deliver a product or service.
109
Verb concepts
Actions those can be carried out on Noun
concepts Such as “Create”, “Update” This
would form sentence like “Create
Customer”, “Update Order”
110
Verification (business analysis)
The process of determining that a
deliverable or artifact meets an
acceptable standard of quality. See also
requirements verification.
111
Verified requirement
A requirement that has been reviewed
and is determined to be defined
correctly, adheres to standards or
guidelines, and is at an acceptable level
of detail.
112
Vertical prototype
A prototype that is used to drill down
into a proposed solution
113
Visual Prototype
Model to test visual aspects of the
solution
114
Walkthrough
A review in which participants step
through an artifact or set of artifacts
115
Workflow modelling
Shows sequence of operations that is
performed Focuses ONLY on human
aspects
116
Yourdon Notation
A notation for DFD
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 48 of 114
Knowledge Area 6 – Solution Evaluation
Sl. #
Solution Evaluation Terms
Definition
1
Accuracy
Closeness between measured value
against true value
2
Business (business world)
An economic system where any
commercial, industrial, or professional
activity is performed for profit.
3
Business constraints
Regulatory statutes, contractual
obligations and Business policies Business
constraints help in setting requirements
priorities
4
Checklist (business analysis)
A standard set of quality elements that
reviewers use for requirements
verification.
5
CMM
Capability maturity model - A model
developed by Software Engineering
Institute
6
Component
A uniquely identifiable element of a larger
whole that fulfills a clear function.
7
Constraint (business analysis)
An influencing factor that cannot be
changed, and that places a limit or
restriction on a possible solution or
solution option.
8
COTS
Commercial off-the-shelf (COTS)
9
Decision tree
A tree structure indicating different
decision options
10
Defect
A deficiency in a product or service that
reduces its quality or varies from a desired
attribute, state, or functionality.
11
End user
A stakeholder who directly interacts with
the solution.
12
Enterprise culture
Enterprise culture may be defined as
deeply rooted values, beliefs, attitudes
and norms shared by its members which
affect their actions
13
Enterprise limitations
Used to understand challenges that exist
within the enterprise
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 49 of 114
Sl. #
Solution Evaluation Terms
Definition
14
Enterprise readiness
assessment
An assessment that describes the
enterprise is prepared to accept the
change associated with a solution and is
able to use it effectively.
15
Existing solutions
Existing products or services, often third
party, which are considered as
components of design option
16
Feature tree
A visual representation of planned
features of a system
17
Financial Dimension
Measures indicating profitability, revenue
growth and added economic value
18
Fishbone diagram
Root cause analysis
19
Fishbone diagrams
Fishbone diagrams (also known as
Ishikawa or Cause-and-effect diagram) are
to identify and organize possible causes
of a problem
20
Five-whys
Five-whys is a process of repeatedly
asking questions to find out the root
cause of a problem
21
Force field analysis
A graphical method for depicting the
forces that support and oppose a change.
22
Guideline (business analysis)
An instruction or description on why or
how to undertake a task.
23
Improvement
Establish ways to increase the probability
or impact of events with a positive impact
24
Indicator
A specific numerical measurement that
indicates progress toward achieving an
impact, output, activity, or input. See also
metric.
25
Inspection
A formal review of a work product by
qualified individuals that follows a
predefined process, and uses predefined
criteria, for defect identification and
removal.
26
Item tracking
Item tracking captures and assigns
responsibility for issues and stakeholder
concerns
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 50 of 114
Sl. #
Solution Evaluation Terms
Definition
27
Lagging indicators
Lagging indicators that provide results of
actions already taken
28
Leading indicators
Leading indicators that provide
information about future performance
29
Non-value-add
aspects and activities for which the
customer is not willing to pay
30
Office productivity tools and
technology
These tools are used to document and
track information and artifacts
31
Organizational culture
deals with the beliefs, values and norms
shared by the members of an organization
32
Performance efficiency
Time taken to perform activities and
resource utilization levels
33
Predictive scorecards
A score card enabling a business decision
34
Presentation Software
Creation of training material, presentation
of information etc
35
Preventive
Establish ways to reduce the probability of
an event with a negative impact,
36
Proactive analysis
Identifying problem areas for preventive
action
37
Product (business analysis)
A solution or component of a solution
that is the result of an initiative.
38
Quality attributes
A set of measures used to judge the
overall quality of a system.
39
Reactive analysis
Identifying root causes for corrective
action
40
Recommended actions
Actions to improve value of a solution
41
Release plan
An activity in Agile where stories are
assigned to various releases
42
Relevant
Aligned with organization’s vision, mission
and goals
43
Repeatability
Same person reaching same conclusion
over a period of time
44
Reproducibility
Different personnel reaching same
conclusion
45
Request for information (RFI)
A formal elicitation method intended to
collect information regarding a vendor's
capabilities or any other information
relevant to a potential upcoming
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 51 of 114
Sl. #
Solution Evaluation Terms
Definition
procurement.
46
Request for proposal (RFP)
A requirements document issued when an
organization is seeking a formal proposal
from vendors.
47
Request for quote (RFQ)
A procurement method of soliciting price
and solution options from vendors.
48
Request for tender (RFT)
An open invitation to vendors to submit a
proposal for goods or services.
49
Requirements defect
A problem or error in a requirement.
50
Root cause
The cause of a problem having no deeper
cause, usually one of several possible
causes.
51
Root cause analysis
A structured examination of an identified
problem to understand the underlying
causes.
52
Scope of Solution Space
Range of solutions that may be
considered
53
SIPOC
Suppliers, inputs, process, outputs and
customers.
54
Solution
A specific way of satisfying one or more
needs in a context.
55
Solution evaluation
Tasks BAs perform to assess the
performance and value delivered by a
solution
56
Solution life cycle
The stages through which a solution
progresses from inception to retirement.
57
Solution limitation
Challenges associated with current
solutions
58
Solution performance goals
Goals for solution performance
59
Solution performance
measures
Current performance of existing solutions
60
Solution recommendations
Possible solutions which can be pursued
in order to achieve the future state
61
Solution scope
The set of capabilities a solution must
deliver in order to meet the business
need.
62
Spreadsheets
Supports Decision analysis through logical
and mathematical manipulations
Giant book of BABoK® V3 Glossary – KA wise
© Adaptive US Be an IIBA Certified BA in 3 months. Guaranteed. Page 52 of 114
Sl. #
Solution Evaluation Terms
Definition
63
SQL
Structured Query Language - A data
management language for RDBMS
systems
64
Statement of work (SOW)
A written description of the services or
tasks that are required to be performed.
65
Suppliers, inputs, process,
outputs, and customers (SIPOC)
A tool used to describe relevant high-level
elements of a process. May be used in
conjunction with process mapping and
‘in/out of scope’ tools, to provide
additional detail.
66
SWOT
SWOT is an acronym for Strengths,
Weaknesses, Opportunities, and Threats
67
Target metric
A target metric is the objective to be
reached within a specified period
68
User acceptance test (UAT)
Assessing whether the delivered solution
meets the needs of the stakeholder group
that will be using the solution. The
assessment is validated against identified
acceptance criteria.
69
Variance
Variance is the difference between
expected and actual performance
70
Vendor assessment
Assess ability of a potential vendor to
meet commitments regarding the delivery
and consistent provision of a product or
service
71
Weighted decision matrix
A decision matrix where evaluation
parameters are given weights reflecting
their criticality
72
Word processing and
presentation programs
Commonly used to develop, format,
present and maintain requirements
------------End of document------------
